home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20030409-20031118
/
000045_hartnuj@uk.ibm.com_Fri May 2 09:21:50 EDT 2003.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
2KB
|
41 lines
Article: 14259 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!phl-feed.news.verio.net!iad-feed.news.verio.net!iad-peer.news.verio.net!news.verio.net!nntp1.roc.gblx.net!nntp.gblx.net!nntp.gblx.net!priapus.visi.com!news-out.visi.com!petbe.visi.com!uunet!ash.uu.net!dfw.uu.net!an02.austin.ibm.com!ausnews.austin.ibm.com!sp15ce20.hursley.ibm.com!not-for-mail
From: John Hartnup <hartnuj@uk.ibm.com>
Newsgroups: comp.protocols.kermit.misc
Subject: Re: can't establish X.509 authenticated connection
Date: Fri, 02 May 2003 11:09:35 +0100
Organization: IBM Hursley
Lines: 18
Message-ID: <b8tg5h$1eq0$1@sp15at20.hursley.ibm.com>
References: <36c7c5aa.0305010725.497e5a04@posting.google.com> <TUdsa.30547$su3.3454739@twister.nyc.rr.com>
NNTP-Posting-Host: dyn-9-140-179-235.warwick.uk.ibm.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: sp15at20.hursley.ibm.com 1051870193 47936 9.140.179.235 (2 May 2003 10:09:53 GMT)
X-Complaints-To: news@hursley.ibm.com
NNTP-Posting-Date: Fri, 2 May 2003 10:09:53 +0000 (UTC)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
In-Reply-To: <TUdsa.30547$su3.3454739@twister.nyc.rr.com>
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14259
Jeffrey Altman [Road Runner NYC] wrote:
>
> You are instructing Kermit to establish a TELNET connection and to
> negotiate the AUTH SSL option. This is incompatible with "openssl
> s_server".
>
Note also that "AUTH SSL" is deprecated, you should use "AUTH TLS"
wherever possible. The only reason to support "AUTH SSL is for
interoperability with old servers. Kermit supports both.
Use "set ftp authtype tls" to specify "AUTH TLS".
To stave off confusion, I'll clarify right now that "AUTH SSL" and "AUTH
TLS" are *not* mechanisms for selecting between SSLv2, SSLv3 and TLSv1:
these are negotiated in the SSL handshake.